Hybris UX Api

Post Customer

This API will allows you to create a Customer entity.

URL

http://[localhost]:[port]/ecom-ux/v1/{businessId}/customer

URL PARAMS

Headers

Data Model - Request

characteristics

Data Model - Response

characteristics

Key considerations

PA Implementation

- name field is a concatenation of firstName and surName.
- idProof valueType represents the identity type of the customer ex Passport(PP),Cedula(C).
- dateOfBirth format must be YYYY-MM-DD.
- characteristic[].name = "type" must have a value of 'RES'.
- characteristic[].name = "sourceEPC" must have a value of 'LIBERATE'.
- companyCode value should be 'CWP'.
- Please refer the Request and response examples with following URL - [Hybris UX Api](https://anypoint.mulesoft.com/exchange/portals/cable-and-wireless/c03653f5-9c46-4e55-bf97-5cef1442bfbf/ecom-ux/minor/1.0/console/method/%2334428/)

CR Implementation

**note**: customerType = "HOTEL" is not in scope and routing is based on lob passed in request body
- New B2C customers are in scope.
- name field in the request is a combination of firstName + lastName + lastName2 from characteristics
- Address fields values should be in Upper case
- No data validation is present in the Mulesoft
- Error message from the backend system is captured in the error response.
- The legacy system that consumes the creation of the customer must respect the values of the lists of values configured in the fields.
- The customer creation web service will only allow the creation of 1 customer at a time.
- The value for the "Identification number" field may be sent with or without hyphens (-), always respecting the minimum and maximum number of characters and other format validations.
- The customer that is created will have as default value in the Status field = "PROSPECT". The proper flow of the Order makes the corresponding change.
- The position and organization of the user consuming the integration will be assigned by default.
- The customer creation process will create an address record with the information provided, this record will be assigned as the main address. The system that consumes the web service must send the correct values from the province, canton, district and neighborhood value lists.
- Mulesoft is converting values to upper case as per the validation in siebel.
- The system will return an error code and message in case there is a problem creating and associating the new address and/or contact record, but the customer creation will not be interrupted. In the case of error (error in address or contact), the creation of these records will be done manually by the end user.
- Reprocessing of request is not possible if the customer entity creation is successful.-Refer Request and Response with Name CR-B2C-Contact Id(contactId), Row Id (id) and Address Id(addressId) are required to Create Agreement, settlementAccount and to create Order-amnistia value should be empty,when “idProofType = CEDULA FISICA” or PASAPORTE

PR Implementation

- name field is the concatenation of firstName and lastName
- DateOfBirth format must be yyyy-MM-dd
- characteristic[].name = "type" must have a value of 'RES'
- characteristic[].name = "sourceEPC" must have a value of 'CSG'
- emailAddress should be mandatory if contactMedium[].mediumType=="Email"

JM Implementation

##### Liberate

- DateOfBirth format must be yyyy-MM-dd.
- characteristic[].name = "type" must have a value of 'RES'
- characteristic[].name = "sourceEPC" must have a value of 'Liberate'

##### Cerillion

- characteristic[].name = "sourceEPC" must have a value of 'Cerillion'